Node / meshtastic / Meshtastic-Android / files / docs / zh-rTW / user / settings-module-admin.md

Displaying Rendered • View raw • Download

title: Settings — Modules & Admin

parent: User Guide

nav_order: 8

last_updated: 2026-05-20

description: Configure optional feature modules (MQTT, telemetry, canned messages, TAK, and more) and perform device administration.

aliases:

• modules

• 模組設定

• administration

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

│ 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces

│ airtime, saves battery, and simplifies your configuration.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

!Toggle switch

!Dropdown selector

!Text field

!Settings card layout

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems.

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node's serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren't lost during brief disconnections.

│ 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes

│ are ideal candidates since they're typically always-on.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

See Telemetry & Sensors for supported sensors and configuration recommendations.

Pre-configured messages accessible from the device's physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

│ ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very

│ low-bandwidth — think "understandable radio voice," not phone-call quality.

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

│ ⚠️ Warning: Enabling "Allow Undefined Pins" gives remote nodes access to all GPIO pins, which

│ could interfere with the radio's own hardware. Only enable on dedicated GPIO nodes.

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

See Discovery for how to use neighbor data for mesh topology exploration.

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

│ 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other

│ locations. Counts are approximate — one person may carry multiple devices.

Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage.

Remotely configure nodes that share your admin key:

1. Select the target node in the node list.

2. Navigate to Settings for that node.

3. Modify configuration.

4. Tap Save — changes are sent over the mesh.

│ ⚠️ Requires: Admin key configured on both your node and the target node.

Removes stale nodes from your local database that haven't been heard in a configurable time window.

Resets all settings to factory defaults. This cannot be undone.

Remotely reboot a connected or administered node.

View detailed diagnostic information:

• Protocol buffers debug output

• Mesh packet log

• Connection state details

• "No response from target node" — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.

• Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.

• Can't see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.

• Settings — Radio & User — core radio and user profile settings

• Module configuration reference — detailed module docs on meshtastic.org

• FAQ — common questions on meshtastic.org